I have a Windows2003R2 Server (printserver). I cannot browse to ONE machine (appserver - Linux Samba 3.5.4 ) using the FQDN to enumerate shares: From printserver: 1. I can browse to \\appserver using the short name : ie net view \\appserver 2. I can browse to \\appserver using the ip address : net view \\192.168.x.x 3. Using net view or explorer, from printserver : net view \\appserver.domain.local returns a System Error 64 has occured. The specified network name cannot be found. 4. DNS returns the correct info doing an nslookup, and the machine can be ping'd with shortname , FQDN and IP with no errors. HOWEVER - I can browse to ANY other machine (wkst/server/linux_samba) on my network using any of the above three methods from printserver. I can also browse to this machine (appserver) using any of the three methods from ANY other wkst/server on the network. I just cannot access one machine by using \\appserver.domain.local from machine printserver. This leads me to believe it is a Windows issue of some sort on this one server - printserver. I have to have Netbios on for print shares and applications. I do not use WINS. DNS is running without error. I have tried adding entries in hosts and lmhosts files on printserver but it di not help. I have not had to do this on ANY of the other servers / workstations - and they have no issues. Thanks in advance.

i think youre having ad integrated dns server which has configured to secure dynamic updates. pls check from your dns server that correct records has created or not?(both forward and reverse zones).Darshana Jayathilake

Hi, Thanks for posting here. In order to troubleshoot this issue, you may try to follow the host name resolution orders to verify if any setting was incorrect. Firstly, please check the local hosts file, then the DNS record, after that is NetBIOS and LMhosts file. In this way, we can narrow down possible cause. Please keep in mind that if the local hosts file has a record about the appserver.domain.local, the name resolution will use this record without query DNS server. In your case, if the hosts file was correct, please try to clear the DNS resolver cache on this server, please run command ipconfig /flushdns, to see if this helps. For NetBIOS, type nbtstat /c to list the cache, use nbtstat /R to clear the name cache. For your more information, please refer to the following articles: Microsoft TCP/IP Host Name Resolution Order http://support.microsoft.com/kb/172218 How to Diagnose and Test TCP/IP or NetBIOS Network Connections in Windows server 2003 http://support.microsoft.com/kb/323388/en-us Best Regards, Aiden